Methods and systems for prefetching music for devices

ABSTRACT

Methods and systems are presented for prefetching music for devices. The disclosed method includes detecting an access to a music library through a device. The music library is associated with a user music account and is managed in cloud music storage. The disclose method further includes monitoring use activities for the user music account and the use activities of selected songs in the music library are adjustable for relevance based on assigned weightings. One or more songs from the music library that satisfy a prefetching constraint based on the monitored use activities are identified. The songs that satisfy the prefetching constraint are tagged for transferring to the device. The tagged songs are transferred to the device without receiving a user initiated request for the tagged songs.

BACKGROUND

Internet applications have grown tremendously over the years and so hasthe functionality provided to devices that access those applications.One area that has seen such growth relates to audio file management. Anaudio file management application enables a user to search and purchasemusic selections online and store the purchased music in cloud storage.Audio file management applications also enable users to access and playmusic stored in the cloud storage using a network connected device. Auser may play a song stored in the cloud storage by clicking an icondisplayed in the display screen of the user device, and the icon isassociated with a song stored in the cloud storage. The song stored inthe cloud storage needs to be downloaded to the user device before thesong can be played. As a result, there is a delay between the time whenthe user clicks on the icon associated with the song and the time whenthe song is played.

It is in this context that embodiments arise.

SUMMARY

Embodiments of the present disclosure provide methods and systems forprefetching music for mobile devices. In one embodiment, at certainpoints in time, only certain music is selected for prefetching. Themusic that is prefetched is, in embodiment, likely to be the music thatwill be selected by a user for play. Thus, reduced delays in download byusing background prefetching will enhance user experience. Over time, asa user listens to different music, the background prefetching will alsochange, mapping to the user's changes in music preferences. It should beappreciated that the present disclosure can be implemented in numerousways, such as a process, an apparatus, a system, a device, or a methodon a computer readable medium. Several inventive embodiments of thepresent disclosure are described below.

In one embodiment, a method for prefetching music for devices isdisclosed. The method includes detecting access to a music librarythrough a device. The music library is managed in cloud music storageand is associated with a user music account. The use activities for theuser music account are monitored and the use activities of selectedsongs in the music library are adjustable for relevance based onassigned weightings. The disclosed method further includes identifyingone or more songs from the music library that satisfy a prefetchingconstraint based on the monitored use activities, and the songs thatsatisfy the prefetching constraint are tagged for transferring to thedevice. The tagged songs are transferred to the mobile device withoutreceiving a user initiated request for the tagged songs. The disclosedmethod may be executed by a processor. In one embodiment, theprefetching constraint of a song in the music library may be measured bycalculating a prefetching score for the song.

In another embodiment, a method for prefetching music for mobile devicesis disclosed. The disclosed method includes identifying if an access toa music library is through a mobile device and transmitting the useactivities for the user music account. The music library is associatedwith the user music account and is managed in cloud music storage. Thetransmitted use activities for the user music account are monitored andthe use activities of selected songs in the music library are adjustablefor relevance based on assigned weightings. The method further includesidentifying one or more songs from the music library that satisfy aprefetching constraint based on the monitored use activities. The songsthat satisfy the prefetching constraint are tagged for transferring tothe mobile device. The tagged songs are received by the mobile devicewithout sending a user initiated request for the tagged songs. Thedisclosed method is executed by a processor.

In yet another embodiment, a system for prefetching music for mobiledevices is disclosed. The system includes a user access module, a deviceidentifier, prefetching logic, and at least one processor configured toexecute the user access module, the device identifier, and theprefetching logic. In one embodiment, the user access module, the deviceidentifier, and the prefetching logic reside in a music manager serverthat manages cloud music storage. The user access module is configuredto detect access to a music library that is associated with a user musicaccount and is managed in the cloud music storage. The device identifieris configured to identify if the detected access is through a mobiledevice. The prefetching logic is configured to monitor the useactivities for the user music account, and the user activities ofselected songs in the music library are adjustable for relevance basedon assigned weightings. The prefetching logic may be further configuredto identify one or more songs from the music library that satisfy aprefetching constraint based on the monitored use activities. The songsthat satisfy the prefetching constraint are tagged for transferring tothe mobile device. In one embodiment, the prefetching logic isconfigured to transfer the tagged songs to the mobile device withoutreceiving a user request for the tagged songs.

In yet still another embodiment, a system for prefetching music formobile devices is disclosed. The disclosed system includes a deviceidentifier, music logic, prefetching logic, and at least one processorconfigured to execute the device identifier, the prefetching logic, andthe music logic. In one embodiment, the device identifier, the musiclogic, and the prefetching logic reside in the mobile device used toaccess a music library managed in cloud music storage. The deviceidentifier is configured to identify if an access to a music library isthrough a mobile device, and the music library is associated with a usermusic account and is managed in cloud music storage. The music logic isconfigured to transmit the use activities for the user music account.The prefetching logic is configured to monitor the use activities forthe user music account and identify one or more songs from the musiclibrary that satisfy a prefetching constraint based on the monitored useactivities. The songs that satisfy the prefetching constraint are taggedfor transferring to the mobile device. The use activities of selectedsongs in the music library are adjustable for relevance based onassigned weightings. The music logic is further configured to receivethe tagged songs by the mobile device without sending a user initiatedrequest for the tagged songs.

Other aspects will become apparent from the following detaileddescription, taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure may best be understood by reference to the followingdescription taken in conjunction with the accompanying drawings.

FIG. 1 illustrates a system diagram for enabling access and playing ofmusic files stored in a cloud music storage, in accordance with oneembodiment of the present disclosure.

FIG. 2 illustrates how user A utilizes a device (e.g. smartphone) toaccess his or her music account stored in the cloud music storage (CMS),in accordance with one embodiment of the present disclosure.

FIG. 3A illustrates a system diagram for prefetching music for a mobiledevice, in accordance with one embodiment of the present disclosure.

FIG. 3B illustrates a system diagram for prefetching music for a mobiledevice, in accordance with one embodiment of the present disclosure.

FIG. 4 illustrates a diagram showing various use activities andassociated weightings recorded in a use metrics for a user musicaccount, in accordance with one embodiment of the present disclosure.

FIG. 5A illustrates a table 500 of exemplary recorded use activitiesalong with assigned use activity values and weightings for song K, inaccordance with one embodiment of the present disclosure.

FIGS. 5B and 5C illustrate dynamically assigned weighting changes basedon monitored use activities from time T0 to time T1, in accordance withone embodiment of the present disclosure.

FIG. 6 illustrates an exemplary user interface for setting up a musicbuffer in a user device, in accordance with one embodiment of thepresent disclosure.

FIG. 7 shows an exemplary update in a music buffer from time t1 to timet2, in accordance with one embodiment of the present disclosure.

FIG. 8A illustrates a flow diagram of an exemplary method forprefetching music for mobile devices, in accordance with one embodimentof the present disclosure.

FIG. 8B illustrates a flow diagram of an exemplary method forprefetching music for mobile devices, in accordance with one embodimentof the present disclosure.

FIG. 9 is a simplified schematic diagram of a computer system forimplementing embodiments of the present disclosure.

DETAILED DESCRIPTION

Methods and systems for prefetching music for devices are disclosed. Themusic to be prefetched is stored in music libraries managed in cloudmusic storage of a digital service provider. In one embodiment, a methodfor prefetching music for devices includes detecting the access to amusic library associated with a user music account through a device. Themethod further includes monitoring the use activities for the user musicaccount and the use activities of selected songs in the music libraryare adjustable for relevance based on assigned weightings. After thesongs from the music library that satisfy a prefetching constraint areidentified based on the monitored use activities, the identified songsare tagged for transferring to the device without receiving a userinitiated request for the tagged songs.

In another embodiment, a method for prefetching music for mobile devicesincludes identifying if an access to a music library is through a mobiledevice and transmitting the use activities for a user music account. Themusic library is associated with the user music account and is managedin cloud music storage. The disclosed method further includes monitoringthe use activities for the user music account and the use activities ofselected songs in the music library are adjustable for relevance basedon assigned weightings. After the songs that satisfy a prefetchingconstraint based on the monitored use activities are identified in themusic library, the identified songs are tagged for transferring to themobile device. The tagged songs are received by the mobile devicewithout receiving a user initiated request for the tagged songs. Thetransferring, therefore, functions as an automatic process that updateswhich songs should be sent to the device (e.g., prefetched), so as tobest satisfy the user's likely selection of songs to play. If thecorrect list of songs are prefetched and stored in the device, therewill be not wait time for download streaming. If most of the user'sselected songs are prefetched, then still the user's experience will beimproved, as the user will not need to wait for downloading of everyselected song.

The following description sets forth numerous specific details such asexamples of specific systems, components, methods, and so forth, inorder to provide a good understanding of several embodiments of thepresent disclosure. It will be apparent to one skilled in the art,however, that at least some embodiments of the present disclosure may bepracticed without these specific details. In other instances, well-knowncomponents or methods are not described in detail or are presented in asimple block diagram format in order to avoid unnecessarily obscuringthe present disclosure. Thus, the specific details set forth are merelyexemplary. Particular implementations may vary from these exemplarydetails and still be contemplated to be within the spirit and scope ofthe present disclosure.

Reference in the description to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification do not necessarily all refer to thesame embodiment.

FIG. 1 illustrates a system diagram 100 for enabling access and playingof music files stored in cloud music storage, in accordance with oneembodiment of the present disclosure. The system 100 includes aplurality of servers that are connected to the Internet 104. Theplurality of servers and storage are, in one embodiment, part of adigital service provider 102. The digital service provider 102, is asystem that can include a plurality of servers that can provideapplications, services, digital content, and interconnectivity betweensystems, applications, users, and social networks. For example, thedigital service provider 102 can include a search engine 108, aplurality of servers 110 that provide applications for various business,social, and technology related subject matter, servers that provide usermanagement 112, and servers to provide music related services 114.

One example digital service provider 102 can be Google Inc., of MountainView Calif. Some digital service providers may be more focused onproviding only specific services, while others provide a variety ofservices for access, download, viewing, searching, etc. The content canvary greatly, but is commonly presented in digital format and displayedon monitors or screens of devices, computers, smartphones, tablets, etc.

The servers that provide music related services, in one embodiment, areillustrated by the music provider logic 114, that executes over one ormore servers that are connected to the Internet 104. The music providerlogic 114 is shown connected to cloud music storage 116. Cloud musicstorage 116 is shown to include a plurality of storage systems,identified as store A, store B, . . . store N. The various storagesystems that hold music data and music metadata, are provided with fastaccess to the Internet, for providing music data on demand to usersrequiring access to their music accounts stored in cloud music storage116. In one embodiment, users can access the cloud music storage 116 byway of a plurality of devices 106. The plurality of devices can includeany type of device having a processor and memory, wired or wireless,portable or not portable. In the example illustrated in FIG. 1, user Ais shown to have device 106 (device A). Device 106 is shown to includecommunication logic for transmitting and receiving data between device106 and the Internet 104.

The communication logic (Tx/Rx) can include various types of networkinterface circuitry, radio-communication (e.g. wireless), cell towercommunication, or interconnected wiring connected to Internet serviceproviders. Device 106 is also shown to include a display having a screen120, local storage 124, and a processor 130. Local storage 124 caninclude cash memory 126, persistent storage 128, and other logic. Inthis example, device 106 is shown to include graphical icons (e.g.,graphical user interfaces GUIs) that represent a play list. The screen120 can be a touch-screen, or a display typically provided by aflat-panel display, a cathode ray tube (CRT), or other media capable ofrendering a display. Still further, device 106 can have its displayseparate from the device, similar to a desktop computer or a laptopcomputer. Still further yet, device 106 can be in the form of asmartphone, a tablet computer, or hybrids that provide touch screencapability in a portable form factor. One example device can include aportable phone device that runs an operating system and is provided withaccess to various applications (apps) that may be obtained over theInternet, and executed on the local portable device (e.g., smartphone,tablet, laptop, desktop, etc.).

In one embodiment, the user of device 106 can install an applicationthat provides cloud storage of music files, and access to the storagecloud music files from device 106. Once the user's music files areuploaded to the cloud music storage 116, the user's music files areassociated to a library of the user. In one embodiment, a plurality ofusers can access the same application and can upload their own musicfiles to create their own libraries, which will be stored in the cloudmusic storage 116.

Each of such users can then access the cloud music storage 116 throughan application on their device 106 to render and play selected musicfiles on their device, when device 106 has access to the Internet andassociated servers of the music provider logic 114 and cloud musicstorage 116. Accordingly, users can access the music application ontheir device 106, access all music files stored in cloud music storage116, arrange music titles in their music library into playlists, addmusic to cloud music storage 116, delete music from cloud music storage116, and purchase music that is added to cloud music storage 116. Thesechanges are maintained and managed by the music provider logic 114 andthe music provider logic 114 will provide access to the various users totheir music files stored in cloud music storage 116, based on theirselections during use of the application.

FIG. 2 illustrates how user A utilizes a device 106 (e.g. smartphone) toaccess his music library stored in cloud music storage 116, inaccordance with one embodiment of the present disclosure. As shown,device 106 will include a screen 120, and associated graphical iconsthat present a thumbnail of an application 140, associated with a musicapplication. Application 140, as described herein, relates to anapplication that provides a user with access to his or her music librarywhich has been previously added to the cloud music storage 116. If theuser is a new user to the application 140, the new user can downloadapplication 140 to device 106 from at least one server 110 of thedigital service provider 102.

Once application 140 has been downloaded and installed on device 106,the icon representing application 140 will be rendered on the displayscreen of device 106. Initially, the user will be prompted to selectmusic to add to cloud music storage 116. The music may be added fromfiles currently maintained by the user on his or her device 106, onother devices of the user such as computers, other smartphone and ortablets, or other storage media. Additionally, the user can add musicfiles that may be part of a music library maintained by anotherapplication. The other application may maintain a specific format forthe music, and the music can be obtained and translated to standardizemusic files for addition to cloud music storage 116.

Once the user has managed his library to add, modify, or adjust themusic files present in cloud music storage 116, the user can accessapplication 140 and various options from graphical user interfacesprovided on the screen 120 of device 106. In the illustrated example,device 106 will open application 140 through various graphical userinterface (“UI”) screens, such as interface 140 a. Interface 140 a caninclude various menus, selection icons, configuration icons, displays,advertisements, buttons, listings, etc. In this example, interface 140 amay include an image that lists the user's library 160, the user'splaylists 162, and music title icons 164. Music title icons can berepresented by graphical artwork that represents artwork associated withthe various music files present in the user's library. The user'slibrary is illustrated by music title icons 164, shown as A-H.

The music title icons 164 are rendered on the screen 120 upon obtainingmetadata from cloud music storage 116 (or accessing the metadata fromprevious download(s) stored locally on the user device), which may bepresent in data store 150. Music provider logic 114 will include requestprocessing module 144 that manages the requests and communicationbetween various users applications 140 and the cloud music storage 116.The request processing module (RPM) 144 is also in communication with aplay processing module (PPM) 146. In order to render the title icons 164on the screen of device 106, music provider logic 114 will utilize therequest processing module 144 to obtain metadata 142 from the data store150.

The metadata 142 will be the metadata associated with the various musicfiles stored in data store 150. The metadata 142 provides informationregarding each of the titles stored in cloud music storage 116, andsufficient information to render the title icons 164 on the screen ofdevice 106, and provides text information, duration information, genreinformation, and other data that describes aspects or characteristics ofthe music files. As shown, when the user selects playlist 162 on device106, a playlist graphical user interface is shown identifying particularsongs that have been arranged by the user.

Playlist A, part of the playlist 162, represents various songs that wereselected by the user. The user can have various playlists, and theselection of playlist A is only provided as one example of a playlistthat includes music files that are played in the order E→D→A→B. Once theuser selects a corresponding play button or clicks on one of the audiofiles in the playlist, the music files will begin to play, via thespeaker 106 a, in the order arranged and defined by the user in his orher playlist A.

FIG. 3A illustrates a system diagram 300A for prefetching music for amobile device, in accordance with one embodiment of the presentdisclosure. The system 300A includes a music manager server 310, a cloudmusic store 320, a social media server 330, and a music store 340.

In one embodiment, music manager server 310 is part of music providerlogic 114, and cloud music store 320 is part of cloud music storage 116,as shown in FIG. 1. In other embodiments, music manager server 310 maybe defined from a separate processing system. For example, music managerserver 310 may be stored in a separate processing system to be accessedby users over Internet 104, and the separate server may work inconjunction with or in coordination with music provider logic 114.

As shown in FIG. 3A, music manager server 310 includes prefetching logic312, a device identifier 314, use context 316, a user access module 317,a user database 318, a music store 319, and tracking logic 390. In oneembodiment, user access module 317 may be used to detect a user's accessto the music library after the user logs into his or her music account.For example, user A may access user A music library 321 after user Alogs into his or her music account 322 that is managed by cloud musicstore 320. Once a user has logged into his or her music account, useraccess module 317 may communicate the user login information to usecontext 316 and device identifier 314. Use context 316, in turn, maysend the user login information to user database 318 to be saved in arecord associated with the user.

In the example illustrated in FIG. 3A, although a user (e.g., user A) isshown to access the services provided by music manager server 310 viaInternet 104, it is to be understood that in practice, many more usersmay access the services provided by music manager server 310, and theservices may be widely distributed across a network. In this example,user A has a user device 350 that has access to an application or codefor accessing user A music account 322 and the online music stored inuser A music library 321. As shown, user device 350 includescommunication logic (Tx/Rx) 351, a music buffer 355, and music logic356. Once user A has established the access to user A music account 322,user device 350 may transmit various use activities related torespective songs stored in user A music library 321. In one embodiment,the use activities for a song in user A music account 322 may betransmitted by music logic 356 via communication logic 351 of userdevice 350. Use context 316 of music manager server 310 may receive thetransmitted use activities for various songs from user device 350 viauser access module 317. For example, after user A has logged into his orher music account 322, use context 316 may start to record user A onlineuse activities related to various songs. The recorded use activities fora song in user A music account may be sent by use context 316 to userdatabase 318 to be stored in user A use metrics 315 of user A record311. User approval of such recording or tracking, is a user optionprovided by an interface.

In one embodiment, user A may access user A music library 321, which isassociated with user A music account 322, through other mobile ornon-mobile devices. User access module 317 may be used to detect allaccesses made by user A (with user permission), either through userdevice 350 or other suitable devices, and to send the received useactivities to use context 316.

In the example shown in FIG. 3A, user A may access social media server330, which maintains a plurality of social network user profiles, viauser access module 317 of music manager server 310. Use context 316 mayrecord the social network interactions obtained from social medialserver 330 via user access module 317. The social network interactionsmay include, without limitation, whether user A has shared a song storedin user A music library 321 with his or her social network friends,whether user A and his or her social network friends like, dislike, orcomment the song, etc. The social network activities of user A may beshared in user A′s social network streams or circles, during live chats,or video chats.

In one embodiment, user database 318 includes a plurality of userrecords, each user record having a music profile portion and a usemetrics portion. For example, user A record 311 includes user A musicprofile 313 and user A use metrics 315. User A music profile 313 maylist user A's music collections, created playlists, favorite songs, etc.The songs in user A's music collection may be stored in user A musiclibrary 321 associated with user A music account 322 in cloud musicstore 320. In one embodiment, user database 318 communicates with cloudmusic store 320 so that the music libraries associated with various usermusic accounts stored in cloud music store 320 may be updated.

Examples of use activities for a song stored in a user music accountincludes, without limitation, number of times the song has been played,number of times the song appears in the playlists created by the user,last time the song was played, ratings of the song, current time of day,social network interactions for the song, purchase time for the song,similarity between the song and other songs in the music library, etc.

In one embodiment, a user may search and purchase online music frommusic store 319, which can be associated or connected to music managerserver 310. Alternatively, the online music may be purchased from themusic store 340 provided by another digital service provider, or onlineretailer. The purchased music may be stored in an associated user musiclibrary managed by cloud music store 320.

In one embodiment, prefetching logic 312 may assign each recorded useactivity with an associated use activity value. The assigned useactivity values may be stored along with the use activities in a usemetrics portion of a user record in user database 318. The assigned useactivity values may vary depending upon the type of use activitiesrecorded. Each assigned use activity may be pre-defined, for example,based on the pre-determined rules of an online music service provider(or defined by the user in advanced settings). In one embodiment, theassigned use activity values ranges from 0 to 1.

In one embodiment, prefetching logic 312 may pull the use metricsportion of each user record in user database 318 at pre-determinedintervals to monitor the documented use activities for the songs storedin a user music library. In one embodiment, prefetching logic 312 maydynamically assign various weightings for each or certain use activitiesof a selected song in the user's music library based on monitored useactivities for the selected song. The assigned weightings may bedynamically adjusted by prefetching logic 312 if the changes to useactivities for the user music account have reached a pre-determinedthreshold. The changes to use activities for a user music account may bedetermined based on time changes, user device location changes, recentuse activity changes, etc. For example, after a song has been playedthree times in a week, the use activity “Number of Times the Song wasPlayed” may be assigned more weighing. In another example, the useactivity “Purchase Time of a Song” for a song may be assigned moreweighting, if the song was purchased recently. The dynamically assignedweightings for the use activities may be used to emphasize ordeemphasize certain use activities when calculating the prefetchingconstraint for the song. In one embodiment, the assigned weighting for ause activity may range from 0 to 1.

In one embodiment, prefetching logic 312 may identify one or more songsfrom the music library that satisfy a pre-defined prefetching constraintsuch that the songs that satisfy the prefetching constraint are taggedfor transferring to the user's device if the use device is a mobiledevice. The prefetching constraint of a song, e.g., may be measured bycalculating a prefetching score for the song based on the assigned useactivity values and weightings for various use activities of the song.If the prefetching score of a song in a user's music library has reacheda pre-determined target score, the song will be tagged to be transferredto the user device if the user device is a mobile device.

In one embodiment, the location of a user device may be tracked bytracking logic 390 (with user permission), that passes the user devicelocation information to prefetching logic 312. In one embodiment,tracking logic 390 may obtain location data from other trackingservices, or location identifying services. For example, locationidentifying services may include, without limitation, signal processingfrom a cellular towers, GPS processors, Wi-Fi signals, IP addressresolution processors, Google Latitude, etc.

In one embodiment, once a user's access to his or her music account hasbeen established, device identifier 314 identifies the user device usedto log into a user's music account to determine whether the user deviceis a mobile device. The identification of a mobile device may bedepended on the connection speed between the mobile device and the musicmanager server that manages the user music library. If the identifieduser device is a mobile device, device identifier 314 informsprefetching logic 312 such that prefetching logic 312 may initiate atransfer of the songs that have been identified to satisfy thepre-defined prefetching constraint to the mobile device withoutreceiving a user request for the identified songs. For example, theidentified songs may be transmitted to user A's user device 350 via useraccess module 317. The transferred songs may be received by music logic356 via communication logic 351 to be stored in music buffer 355 of userdevice 350.

In one embodiment, music buffer 355 in user device 350 may be set up byuser A via a music buffer setup application. For example, user A maysetup the size of music buffer 355 and the size of prefetch. The size ofprefetch may be used as a threshold such that when the number of songsthat have been tagged for transfer to the user device has reached thesize of prefetch, the transmitting of the tagged songs to the mobiledevice starts to take place. In one embodiment, music logic 356 maymonitor the available size of music buffer 355. If the available size ofmusic buffer 355 is less than the size of the songs to be transmittedfrom music manager server 310, music logic 356 may delete the songs inmusic buffer 355 based on pre-defined deleting constraint so that musicbuffer 355 has enough space to store the songs transmitted byprefetching logic 312 of music manager server 310. Examples ofpre-defined deleting constraint for a song stored in a music bufferinclude, without limitation, the song has not been played for a certainperiod of time, the song was downloaded one month ago, etc.

FIG. 3B illustrates a system diagram 300B for prefetching music for amobile device, in accordance with one embodiment of the presentdisclosure. The system 300B includes a music manager server 310′, cloudmusic store 320, a social media server 330, and a music store 340. Inthe example illustrated in FIG. 3B, a user (e.g., user B) may access theservices provided by music manager server 310′. It is to be understoodthat in practice, many more users may access the services provided bymusic manager server 310′, and the services may be widely distributedacross a network. In this example, user B has a user device 360 with anapplication or code for accessing user B music account 325 and theonline music stored in user B music library 326.

In one embodiment, music manager server 310′ is part of music providerlogic 114, and cloud music store 320 is part of cloud music storage 116,as shown in FIG. 1. In other embodiments, music manager server 310′ maybe defined from a separate processing system. For example, music managerserver 310′ may be stored in a separate processing system to be accessedby users over Internet 104, and the separate server may work inconjunction with or in coordination with music provider logic 114.

As shown in FIG. 3B, music manager server 310′ includes a user accessmodule 317, a user database 318, a music store 319, and tracking logic390. In one embodiment, user access module 317 may be used to detect auser's access to his or her music account. In one embodiment, a user mayestablish access to his or her music account by logging into his or hermusic account. User access module 317 may communicate the user logininformation to user database 318. The user login information may besaved in a record associated with the user in user database 318. Forexample, after user B has logged into his or her music account 325online, user access module 317 will send user B's login information touser database 318 to be stored in user B record 311′. User database 318may include a plurality of user records with each user record beingassociated with a user and documenting the use activities for the user'smusic account. In one embodiment, user B may purchase music online frommusic store 319, which can be associated or connected to the musicmanager server 310′. Alternatively, the online music may be purchasedfrom music store 340 provided by another digital service provider, oronline retailer.

In the example illustrated in FIG. 3B, user B's user device 360 includescommunication logic (Tx/Rx) 361, prefetching logic 363, a deviceidentifier 364, a music buffer 365, and music logic 366. Thecommunication logic 361 includes various types of network interfacecircuitry, radio-communication (e.g. wireless), cell towercommunication, or interconnected wiring connected to Internet serviceproviders, and may be used for transmitting and receiving data betweenuser device 360 and music manager server 310′ through Internet 104. Inone embodiment, music logic 366 may be used to transmit various useactivities conducted by user B to music manager server 310′ and receivethe prefetched songs from music manager server 310′ via communicationlogic 361.

In one embodiment, similar to the embodiment shown in FIG. 3A, each userrecord in user database 318 of music manager server 310′ includes a usermusic profile portion and a user use metrics portion. For example, userB record 311′ includes user B music profile 313′ and user B use metrics315′. User B music profile 313′ may list user B′s music collections,created playlists, favorite songs, etc. The songs in user B's musiccollection may be stored in user B music library 326, which isassociated with user B music account 325 in cloud music store 320. Inone embodiment, user database 318 communicates with cloud music store320 so that the music libraries of the various user music accountsstored in cloud music store 320 may be updated.

In the example illustrated in FIG. 3B, user B may access social mediaserver 330 that maintains a plurality of social network user profilesvia communication logic 361. User B may share or comment on a song andchat with his or her social network friends while listening to music orperforming other online activities. Those social network interactionsmay be sent by music logic 366 to music manager server 310′ to be savedin user B use metrics 315′ of user B record 311′.

Examples of use activities for a song stored in a user music accountincludes, without limitation, number of times the song has been played,number of times the song appears in the playlists created by the user,last time the song was played, ratings of the song, current time of day,social network interactions for the song, purchase time for the song,similarity between the song and other songs in the music library, etc.

In one embodiment, device identified 364 in user device 360 may identifyif user device 360 is a mobile device. The identification of user device360 may depend on the connection speed between user device 360 and musicmanager server 310′. If user device 360 is a mobile device, deviceidentifier 364 informs prefetching logic 363 so that prefetching logic363 may start to monitor the use activities stored in user B use metrics315′ by pulling the music manager server 310′ at pre-determined timeintervals.

In one embodiment, prefetching logic 363 may assign each recorded useactivity with an associated use activity value. The assigned useactivity values may be stored along with the use activities in a usemetrics portion of a user record in user database 318. The assigned useactivity values may vary depending upon the type of use activitiesrecorded. Each assigned use activity may be pre-defined based on thepre-determined rules of an online music service provider. In oneembodiment, the assigned use activity values ranges from 0 to 1.

In one embodiment, prefetching logic 363 may dynamically assign aweighting to each or selected use activities for a song stored in user Bmusic library 326 based on monitored use activities. The assignedweightings may range from 0 to 1. The assigned weightings may berecorded in user B use metrics 315′ as well. The assigned weightings tovarious use activities may be dynamically adjusted by prefetching logic363 if the changes to use activities for user B music account 325 havereached a pre-determined threshold. Examples of changes to useactivities for a user music account include, without limitation, timechanges, user device location changes, recent use activity changes, etc.For example, the use activity “Purchase Time of a Song” may be assigneda higher weighting if the song was purchased within a week. In anotherexample, the use activity “Number of Times a Song was Played” may beassigned a higher weighting after the song has been played three timesin a week, which reaches the pre-determined threshold.

The location of a user device may be tracked by tracking logic 390 thatpasses the user device location information to prefetching logic 363 viauser access module 317 and communication logic 361. In one embodiment,tracking logic 390 may obtain location data from other trackingservices, or location identifying services. For example, locationidentifying services may include, without limitation, signal processingfrom a cellular towers, GPS processors, Wi-Fi signals, IP addressresolution processors, Google Latitude, etc.

In one embodiment, prefetching logic 363 may identify one or more songs,stored in user B music library 326, that satisfy a prefetchingconstraint, such that the songs that satisfy the prefetching constraintare tagged for transferring to user device 360. For example, theprefetching constraint for a song may be measured by calculating theprefetching scores for the song based on the assigned use activityvalues and weightings for various use activities.

In one embodiment, prefetching logic 363 may initiate a transfer oftagged songs that satisfy the prefetching constraint from user B musiclibrary 326 stored in cloud music store 320 to user device 360. In oneembodiment, the receiving of the tagged songs by user device 360 isautomatically initiated without receiving user B's request for thetagged songs. In one embodiment, music logic 366 of user device 360 mayreceive the tagged songs via user access module 317 of the music managerserver 310′ and communication logic 361 of user device 360. The receivedsongs may be stored in music buffer 365.

In one embodiment, music buffer 365 may be set up by user B via a musicbuffer setup application (e.g., options menus) previously installed oraccessible via user device 360. For example, user B may setup the sizeof music buffer 365 and the size of prefetch. The size of prefetch maybe used as a threshold such that user device 360 does not receive anytagged songs from music manager server 310′ until the number of songsthat have been tagged for transfer has reached the number of songsdefined by the size of prefetch. In one embodiment, music logic 366 maymonitor the available size of music buffer 365. If the available size ofmusic buffer 365 is less than the size of the songs to be received frommusic manager server 310′, music logic 366 may delete the songs in musicbuffer 365 based on pre-defined deleting constraint so that music buffer365 has enough space to store the received songs. Examples ofpre-defined deleting constraint for a song stored in a music bufferinclude, without limitation, the song has not been played for a month,the song has only been played once after download, etc.

FIG. 4 illustrates a diagram 400 showing various use activities andassociated weightings recorded in a use metrics for a user musicaccount, in accordance with one embodiment of the present disclosure. Inone embodiment, the use metrics may be stored in a use metrics portionof a user record in user database 318, as shown in FIG. 3A and FIG. 3B.

In the example shown in FIG. 4, use metrics 401 may record the followinguse activities for the songs stored in the music library of a user'smusic account: time of day 402, social network interactions 403,purchase time 404, similarity between songs 405, and use profiles 406.Examples of use profiles 406 of a song may include, without limitation,number of times the song has appeared in the playlists created in theuser music account, play counts of the song, the time when the song waslast played, the rating of the song, etc.

In one embodiment, each recorded use activity in use metrics is assignedan associated use activity value based on pre-defined rules of an onlinemusic service provider. The use activity value for each use activity mayvary based on the type of use activities. For example, the use activity“Last Time a Song was Played” may be assigned a higher use activityvalue, while the use activity “Time of Day” may be assigned a lower useactivity value.

In one embodiment, weightings 407 may be dynamically assigned, e.g., byprefetching logic 312 shown in FIG. 3A or prefetching logic 363 shown inFIG. 3B, to each or certain recorded use activities for particular songsbased on pre-determined rules. The assigned weightings 407 are alsorecorded in use metrics 401. Weightings 407 may be used to emphasize ordeemphasize certain use activities compared to others for themeasurement of prefetching constraint.

In one embodiment, the assigned weightings 407 may be dynamicallyadjusted by prefetching logic 312 or prefetching logic 363 if changes touse activities have reached a pre-determined threshold. For example, ifthe current time is at or close to the time when the song was lastplayed, the weighting assigned to the use activity “time of day 402” maybe increased, thus increasing the prefetching constraint of the song. Inanother example, if a song was purchased within a pre-defined timeperiod, use activity “purchase time 404” of the song may be emphasizedby increasing its assigned weighting. In yet another example, if theuser has recently purchased more songs that are similar to the song theuse activities of which are monitored, the weighting assigned to useactivity “similarity between songs 405” for the song may be increased.

FIG. 5A illustrates a table 500 of exemplary recorded use activitiesalong with assigned use activity values and weightings for song K, inaccordance with one embodiment of the present disclosure. In oneembodiment, the use metrics may be saved in an associated user record ina user database, e.g., user database 318, as shown in FIG. 3A and FIG.3B.

As shown, example recorded use activities for song K in are: last timesong K was played, ratings of song K, number of times song K was played,number of times song K appeared in playlists, time of day, purchase timeof song K, and social network interactions of song K. As shown, eachrecorded use activity for song K is assigned an associated use activityvalue, e.g., A1, A2, . . . A7, and each recorded use activity for song Kis assigned a weighting, e.g., Wt1, Wt2, Wt3, Wt7. In one embodiment,the assigned use activity values are pre-defined based on pre-determinedrules of an online music service provider, while the assigned weightingsare dynamically adjustable based on the monitored use activity changes.In one example, the use activity values and the weightings may beassigned by prefetching logic 312 or prefetching logic 363, as shown inFIG. 3A and FIG. 3B.

In this embodiment, an assigned weighting is a value between 0 and 1,where 0 is low importance and 1 is high importance. In still otherembodiments, weighting values can be larger than 1 and less than 0. Inthe main example, if a particular use activity is, at some point in timeimportant, the weighing assigned to the use activity can be closed to 1,such as 0.85. If a use activity is determined to be of low importance,the weighting assigned can be close to 0, such as 0.1 or 0. In a morespecific example, if the use activity “Number of Times Song K wasPlayed” is initially assigned a weighting having a value of 0.5, theassigned weighting can be dynamically changed to 1 if song K has beenplayed three times a day recently. Similarly, each of the assigned useactivity values is a value between 0 and 1, where 0 is low importanceand 1 is high importance. The importance of each use activity has beenpre-determined.

In one embodiment, the prefetching constraint of song K may be measuredby calculating a prefetching score based on the recorded use activitiesof song K. A prefetching score of a song may be calculated by Σ (UseActivity Value (i)×assigned Weighting (i)/Total Number of UseActivities, where i=1 . . . Total Number of Use Activities.

For example, the total number of recorded use activities in FIG. 5A is7, and the prefetching score of song K based on the recorded useactivities may be calculated as:Prefetching Score of Song K=Σ(A1×Wt1+A2×Wt2 . . . +A7×Wt7)/7

where A1 to A7 are the use activity values for the recorded useactivities and Wt1 to Wt7 are respectively assigned weightings. In oneembodiment, the use activity values and the associated weightings may beassigned by prefetching logic 312 (FIG. 3A) or prefetching logic 363(FIG. 3B).

FIGS. 5B and 5C illustrate dynamically assigned weighting changes basedon monitored use activities from time T0 to time T1, in accordance withone embodiment of the present invention. As shown in FIG. 5B and FIG.5C, the use activity values, ranging from 0 to 1, for the recorded useactivities are pre-defined based on the importance of each use activityby an online music service provider. In one embodiment, the assigned useactivity values may not be adjustable based on the monitored useactivity changes. For example, the use activity “Last Time Song K wasPlayed” has been determined to be the most important use activity,thereby being given a use activity value of 0.9. While the use activity“Time of Day” has been determined to be the least important useactivity, thereby being given a use activity value of 0.2.

FIG. 5B shows the assigned use activity values and weightings at T0. Attime T0, the use activity “Number of Times Song K Appeared in Playlists”has been given the most emphasis with a weighing value of 1, while theuse activity “Social Network Interactions of Song K” has been given theleast emphasis with a weighting value of 0.2. As shown in FIG. 5C, attime T1, the use activity “Last Time Song K was Played” has been giventhe most emphasis, because song K was playing at or just played prior toTime T1. As a result, the assigned weighting of for this use activityhas been dynamically adjusted from 0.5 (at time T0) to 1 (at time T1).Also, the use activity “Number of Times Song K Appeared in Playlists”has been deemphasized because the number of playlists that include songK has reduced, Thus, the weighting assigned for this use activity hasbeen adjusted from 1 (at time T0) to 0.5 (at time T1). In addition, attime T1, the use activity “Social Network Interactions of Song K” hasbeen emphasized, with the weighting changes from 0.2 (at time T0) to 0.8(at time T1), based on the increased social network interactions forsong K.

Accordingly, the prefetching score of song K at timeT0=(0.9×0.5+0.8×0.5+0.8×0.8+0.7×1+0.2×0.4+0.4×0.6+0.6×0.2)/7=0.3757

The prefetching score of song K at timeT1=(0.9×1+0.8×0.5+0.8×0.8+0.7×0.5+0.2×0.4+0.4×0.6+0.6×0.8)/7=0.4414

If the target score for the prefetching constraint of song K is 0.4,then song K at time T1 satisfies the prefetching constraint. This means,that song K should be automatically prefetched and added to the user'sdevice storage. This process happens automatically, as either a cloudprocess, a device process, or a combination of cloud and device sharedprocess. Furthermore, although the example was provided for one song K,the process is repeated or processed for all songs in the user'slibrary, which will identify each of the songs that will beautomatically prefetched.

FIG. 6 illustrates an exemplary user interface for setting up a musicbuffer in a user device, in accordance with one embodiment of thepresent disclosure. As shown in FIG. 6, user device 610 includes adisplay screen 620. An application for setting up a music buffer in userdevice 610 has been installed in user device 610 and the user interfaceof the installed set up application is rendered on display screen 620. Auser may choose to set up the maximum space of the music buffer (e.g.,1G, 2G, . . . 5G) and the size of prefetch for tagged songs (e.g., 15songs, 25 songs, . . . 50 songs). The size of prefetch may define a songtransferring threshold such that the use device 610 does not receive anytagged songs until the number of tagged songs has reached the number ofsongs defined by the size of prefetch.

Although FIG. 6 shows a music buffer in a user device may be set up bytwo pull down menus, it is to be understood that a music buffer in auser device may be set up by other suitable means rendered in the userinterface of the user device, e.g., radio buttons, check boxes, voice,gestures, etc.

FIG. 7 shows an exemplary update in a music buffer 700 from time t1 totime t2, in accordance with one embodiment of the present disclosure. Inone embodiment, music buffer 700 is located in a user device, e.g., userdevice 360 and is managed by music logic, e.g., music logic 366, asshown in FIG. 3B.

In the embodiment shown in FIG. 7, at time t1, music buffer 700 is fullwith N number of songs, e.g., S1, S2, S3, S4, S5, . . . Sn. At time t2,two other songs Sn+1 and Sn+2, which are tagged by prefetching logic,e.g., prefetching logic 363 of music manager server 310′ in FIG. 3B,need to be transmitted and saved in music buffer 700. Since music buffer700 was full, songs, stored in music buffer 700, that satisfy a deletingconstraint need to be deleted. In this example, songs S3 and S5 aredeleted based on the deleting constraints of songs S3 and S5 measured attime t2. For example, songs S3 and S5 may be deleted because songs S3and S5 have not been played for a certain period of time or becausesongs S3 and S5 have been played with limited number of times after thedownloads. In another example, songs S3 and S5 may be deleted becausethe user has recently purchased and uploaded new songs to his or hermusic account that are different in type than songs S3 and S5.

It is to be understood that whether any songs need to deleted from amusic buffer may depend on the size of the user music library. Forexample, if a user has a small music collection and the number of songsin the user's music library is less than the maximum available size ofthe music buffer, in this case, no deletion of songs is needed from themusic buffer.

FIG. 8A illustrates a flow diagram of an exemplary method 800A forprefetching music for mobile devices, in accordance with one embodimentof the present disclosure. In one embodiment, the illustrated exemplarymethod 800A is described in relation to operations performed by themusic manager server 310, as shown in FIG. 3A. As used herein, the term“music manager server” is used to connote a system that can manage themusical prefetching functionality for users. As such, so long as thefunctionality is provided, any name may be provided for “music managerserver.”

In operation 810A, an access to a music library is detected. The accessto the music library may be conducted through a user device. Forexample, a user may use his or her user device to log into his or hermusic account in order to access the music library associated with thisuser music account. The music library may be managed in cloud musicstorage, for example, cloud music store 320 of cloud music storage 116,as shown in FIG. 3A. In one embodiment, the access is detected by useraccess module 317 of music manager server 310, as shown in FIG. 3A.

In operation 820A, the user device used to access the music library isidentified to determine if the user device is a mobile device. In oneembodiment, device identifier 314 may be utilized to identify whetherthe user device used to access the user music library is a mobiledevice. In one embodiment, whether a user device is a mobile device isidentified through the connection speed between the user device and themusic manager server that manages the music library of the user.

In operation 830A, the use activities for the user music account aremonitored. In one embodiment, prefetching logic 312 may periodicallypull the associated user record to monitor the recorded use activitiesfor the user music account. The use activities of selected songs in themusic library are adjustable for relevance based on dynamically assignedweightings. For example, the use activity “Purchase Time of a Song” maybe assigned more weighting after the song has been purchased recently.

In one embodiment, prefetching logic 312 may be used to assign one ormore weightings to the use activities of particular songs in the usermusic library and monitor the use activities of the songs. The assignedweightings may be dynamically adjusted by, for example, prefetchinglogic 312, if changes to the use activities have reached pre-determinedthresholds. The changes to the use activities may be determined based ontime, location of the user device, recent use activities changes, etc.In one embodiment, the use activities for a user music account arerecorded in a use metrics portion of a user record that is associatedwith the user in user database 318.

Examples of use activities for a song stored in a user music accountinclude, without limitation, number of times the song has been played,number of times the song appears in the playlists created by the user,last time the song was played, ratings of the song, current time of day,social network interactions for the song, purchase time for the song,similarity between the song and other songs in the music library, etc.

In operation 840A, one or more songs from the music library that satisfya prefetching constraint are identified based on the monitored useactivities, and the songs that satisfy the prefetching constraint aretagged for transferring to the mobile device. In one embodiment,prefetching logic 312 may be used to identify the songs that satisfy theprefetching constraint. The prefetching constraint may be measured bycalculating a prefetching score for a song.

In operation 850A, the tagged songs that satisfy the prefetchingconstraint may be transferred to the mobile device. The transferring isinitiated without receiving a user initiated request for the taggedsongs. In one embodiment, prefetching logic 312 may be used to transferthe tagged songs to the identified mobile device via user access module317.

In one embodiment, prefetching logic 312 may receive a parameter, e.g.,the size of prefetch, which defines a song transferring threshold. Thesong transferring threshold may be set up by either the user or thedigital music service provider. For example, prefetching logic 312 maynot transmit any tagged songs until the number of the tagged songsreaches the song transferring threshold. Alternatively, prefetchinglogic 312 may start to transfer the tagged songs at the pre-defined timeintervals, regardless the number of tagged songs.

FIG. 8B illustrates a flow diagram of an exemplary method 800B forprefetching music for mobile devices, in accordance with one embodimentof the present disclosure. In one embodiment, the illustrated exemplarymethod 800B is described in relation to operations performed by thesystem 300B as shown in FIG. 3B. As shown in FIG. 3B, user device 360includes communication logic 361, prefetching logic 363, a deviceidentifier 364, a music buffer 365, and music logic 366.

In operation 810B, an access to a music library is identified todetermine if the access is through a mobile device. The music library isassociated with a user music account and the music library is managed incloud music storage. In one embodiment, the access to the music libraryis conducted through user device 360. For example, device identifier 364may identify user device 360 through the connection speed between musicmanager server 310′ and user device 360. After device identifier 364 hasdetermined that user device 360 is a mobile device, device identifier364 may notify prefetching logic 363.

In operation 820B, the use activities for the user music account aretransmitted. In one example, the use activities for user B music account325 may be transmitted by music logic 366 via communication logic 361 ofuser device 360. The transmitted use activities may be received by musicmanager server 310′ via user access module 317 to be saved in user B usemetrics 315′ of user B record 311′ stored in user database 318.

In one embodiment, the use activities for a song in a user music accountinclude, without limitation, number of times the song has been played,number of times the song appears in the playlists created by the user,last time the song was played, ratings of the song, current time of day,social network interactions for the song, purchase time for the song,similarity between the song and other songs in the music library, etc.

In operation 830B, the transmitted use activities are monitored and theuse activities of selected songs in the music library are adjustable forrelevance based on dynamically assigned weightings. In one embodiment,prefetching logic 363 may be used to assign one or more weightings tothe use activities of particular songs in user B music library 326 ofuser B music account 325. The assigned weightings may be dynamicallyadjusted by, for example, prefetching logic 363, if changes to useactivities have reached a pre-determined threshold. The changes to theuse activities may be determined based on time, location of the userdevice, recent use activities changes, etc.

In operation 840B, one or more songs from the music library that satisfya prefetching constraint based on the monitored use activities areidentified. The songs that satisfy the prefetching constraint are taggedfor transferring to the mobile device. In one embodiment, prefetchinglogic 363 may be used to identify the songs that satisfy the prefetchingconstraint by pulling user B use metrics 315′ of user B record 311′stored in user database 318. In one embodiment, the prefetchingconstraint may be measured by calculating a prefetching score for asong.

In operation 850B, the tagged songs that satisfy the prefetchingconstraint may be received by the mobile device. The receiving isinitiated without sending a user initiated request for the tagged songs.In one embodiment, music logic 366 may be used to receive the taggedsongs and store the received tagged songs to music buffer 365.

In one embodiment, a user may set up a song transferring threshold froma user device such that no tagged songs are received by the user deviceunless the number of tagged songs has reached the song transferringthreshold. Alternatively, the tagged songs are received by a user deviceat the pre-defined time intervals, regardless the number of taggedsongs.

FIG. 9 is a simplified schematic diagram of a computer system 900 forimplementing embodiments of the present disclosure. FIG. 9 depicts anexemplary computer environment for implementing embodiments of thedisclosure. It should be appreciated that the methods described hereinmay be performed with a digital processing system, such as ageneral-purpose computer system. Special purpose computers, which aredesigned or programmed to perform only one function, may be used in thealternative. The computer system 900 includes a processor 904, which iscoupled through a bus to memory 906, permanent storage 908, andInput/Output (I/O) interface 910.

Permanent storage 908 represents a persistent data storage device suchas a hard drive or a USB drive, which may be local or remote. Networkinterface 912 provides connections via network 914, allowingcommunications (wired or wireless) with other devices. It should beappreciated that processor 904 may be embodied in a general-purposeprocessor, a special purpose processor, or a specially programmed logicdevice. Input/Output (I/O) interface 910 provides communication withdifferent peripherals and is connected with processor 904, memory 906,and permanent storage 908, through the bus. Sample peripherals includedisplay 922, keyboard 918, mouse 920, removable media device 916, etc.

Display 922 is configured to display the user interfaces describedherein. Keyboard 918, mouse 920, removable media device 916, and otherperipherals are coupled to I/O interface 910 in order to exchangeinformation with processor 904. It should be appreciated that data toand from external devices may be communicated through I/O interface 910.Embodiments of the disclosure can also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a wired or a wireless network.

Embodiments of the present disclosure can be fabricated as computerreadable code on a non-transitory computer readable storage medium. Thenon-transitory computer readable storage medium holds data which can beread by a computer system. Examples of the non-transitory computerreadable storage medium include permanent storage 908, network attachedstorage (NAS), read-only memory or random-access memory in memory module906, Compact Discs (CD), Blu-ray™ discs, flash drives, hard drives,magnetic tapes, and other data storage devices. The non-transitorycomputer readable storage medium may be distributed over anetwork-coupled computer system so that the computer readable code isstored and executed in a distributed fashion.

Additionally, FIG. 9 shows various types of devices that can connect tothe network, such as the internet. The devices include servers, tabletcomputers, smartphones, laptops, desktops, etc. The various devices runoperating systems and the operating systems can vary from manufacturerto manufacturer.

Some, or all operations of the method presented herein are executedthrough a processor, such as processor 904 of FIG. 9. Additionally,although the method operations were described in a specific order, itshould be understood that some operations may be performed in adifferent order, when the order of the operations do not affect theexpected results. In addition, other operations may be included in themethods presented, and the operations may be performed by differententities in a distributed fashion, as long as the processing of theoperations is performed in the desired way.

In addition, at least one operation of some methods performs physicalmanipulation of physical quantities, and some of the operationsdescribed herein are useful machine operations. Embodiments presentedherein recite a device or apparatus. The apparatus may be speciallyconstructed for the required purpose or may be a general purposecomputer. The apparatus includes a processor capable of executing theprogram instructions of the computer programs presented herein.

Although the foregoing embodiments have been described with a certainlevel of detail for purposes of clarity, it is noted that certainchanges and modifications can be practiced within the scope of theappended claims. Accordingly, the provided embodiments are to beconsidered illustrative and not restrictive, not limited by the detailspresented herein, and may be modified within the scope and equivalentsof the appended claims.

What is claimed is:
 1. A method for prefetching music for devices,comprising: detecting access to a music library that is associated witha user music account from a device, the music library being managed incloud music storage; determining a connection speed between the deviceand a music manager server that manages the cloud music storage;identifying that the device is a mobile device based upon the connectionspeed; monitoring use activities of selected songs in the music libraryfor the user music account, wherein the use activities of selected songsin the library are adjustable for relevance based on assignedweightings; in response to identifying that the device is a mobiledevice: identifying one or more songs from the music library thatsatisfy a prefetching constraint based on the monitored use activities,wherein the one or more songs that satisfy the prefetching constraintare tagged for transfer to the device; transferring the one or moretagged songs to the device, the transferring being initiated withoutreceiving a user initiated request for the one or more tagged songs. 2.The method of claim 1, further comprising, dynamically changing theassigned weightings if changes to the use activities have reached apre-determined threshold.
 3. The method of claim 1, wherein theprefetching constraint of a song in the music library is measured bycalculating a prefetching score for the song.
 4. The method of claim 1,wherein the one or more tagged songs are transferred to the device whennumber of one or more tagged songs has reached a song transferringthreshold.
 5. A method for prefetching music for mobile devices,comprising: identifying an access from a device to a music library;determining a connection speed between the device and a music managerserver that manages a cloud music storage, the music library beingassociated with a user music account and being managed in the cloudmusic storage; transmitting use activities for the user music account;monitoring the transmitted use activities of selected songs in the musiclibrary for the user music account, wherein the transmitted useactivities are adjustable for relevance based on assigned weightings; inresponse to determining that the device is a mobile device according tothe determined connection speed: identifying one or more songs from themusic library that satisfy a prefetching constraint based on themonitored use activities, wherein the one or more songs that satisfy theprefetching constraint are tagged for transferring to the mobile device;and receiving the one or more tagged songs by the mobile device, thereceiving being initiated without sending a user initiated request forthe one or more tagged songs.
 6. The method of claim 5, furthercomprising: dynamically changing the assigned weightings if changes tothe monitored use activities have reached a pre-determined threshold. 7.The method of claim 5, wherein the prefetching constraint of a song inthe music library is measured by calculating a prefetching score for thesong.
 8. The method of claim 5, wherein the receiving of the taggedsongs further includes, determining available size in a music buffer ofthe mobile device; if the available size in the music buffer is smallerthan size of the one or more tagged songs to be received, identifyingone or more songs in the music buffer that satisfy a deletingconstraint; deleting the one or more songs that satisfy the deletingconstraint in the music buffer; and storing the one or more tagged songsin the music buffer of the mobile device.
 9. The method of claim 5,wherein the receiving of the one or more tagged songs further includes,setting up a song transferring threshold; and receiving the one or moretagged songs by the mobile device when number of the tagged songs hasreached the song transferring threshold.
 10. A system for prefetchingmusic for mobile devices, comprising: a user access module configured todetect access to a music library that is associated with a user musicaccount, the music library being managed in cloud music storage; adevice identifier configured to determine a connection speed between amobile device and a music manager server that manages the cloud musicstorage and identify that the detected access is through the mobiledevice based upon the connection speed; prefetching logic configured tomonitor use activities for the user music account, wherein the useactivities of selected songs in the music library are adjustable forrelevance based on assigned weightings, identify one or more songs fromthe music library that satisfy a prefetching constraint based on themonitored use activities, and songs that satisfy the prefetchingconstraint being tagged for transferring to the mobile device, and inresponse to identification that the detected access is through themobile device, transfer the tagged songs to the mobile device, thetransferring being initiated without receiving a user initiated requestfor the tagged songs; and at least one processor configured to executethe user access module, the device identifier, and the prefetchinglogic.
 11. The system of claim 10, wherein the user access module, thedevice identifier, and the prefetching logic reside at a music managerserver that manages the cloud music storage.
 12. The system of claim 10,further comprising: a user database that includes a plurality of userrecords, each user record having a use metrics portion.
 13. The systemof claim 12, wherein the use activities for the user music account arerecorded in the use metrics portion of a user record associated with theuser music account.
 14. The system of claim 10, further comprising: amusic buffer in the mobile device configured to store the transmittedsongs.
 15. A system for prefetching music for mobile devices,comprising: a device identifier configured to determine a connectionspeed between a device and a music manager server that manages a cloudmusic storage and identify that the device is a mobile device based uponthe connection speed, a music library being associated with a user musicaccount and being managed in the cloud music storage; music logicconfigured to transmit use activities for the user music account;prefetching logic configured to monitor the transmitted use activitiesfor the user music account, wherein use activities of selected songs inthe music library are adjustable for relevance based on assignedweightings, and identify one or more songs from the music library thatsatisfy a prefetching constraint based on the monitored use activities,wherein the one or more songs that satisfy the prefetching constraintare tagged for transferring to the mobile device in response to theidentification that the device is a mobile device; the music logicconfigured to receive the one or more tagged songs by the mobile device,the receiving of the one or more tagged songs being initiated withoutsending a user initiated request for the one or more tagged songs; andat least one processor configured to execute the device identifier, theprefetching logic, and the music logic.
 16. The system of claim 15,wherein the device identifier, the music logic, and the prefetchinglogic reside in the mobile device.
 17. The system of claim 15, whereinthe music logic is further configured to: determine available size in amusic buffer; if the available size in the music buffer is smaller thansize of the one or more tagged songs to be received, identifying one ormore songs in the music buffer that satisfy a deleting constraint;deleting the one or more songs that satisfy the deleting constraint inthe music buffer; and storing the one or more tagged songs in the musicbuffer.
 18. The system of claim 15, wherein the music logic is furtherconfigured to set up a song transferring threshold; and receive the oneor more tagged songs by the mobile device when number of the one or moretagged songs has reached the song transferring threshold.
 19. The systemof claim 15, further comprising: a user database that includes aplurality of user records, wherein the transmitted use activities alongwith the assigned weightings are stored in a user record associated withthe user music account.